-
Notifications
You must be signed in to change notification settings - Fork 97
feat: Use slog for logging #1898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
arthurpitman
wants to merge
4
commits into
main
Choose a base branch
from
feat/use-slog
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
E2E Test Results 3 files ±0 257 suites - 6 20m 50s ⏱️ + 2m 11s For more details on these failures, see this check. Results for commit 3f70c4f. ± Comparison against base commit e0c6ee6. This pull request removes 18 and adds 9 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
9e2b34e
to
d8dc543
Compare
d8dc543
to
9540252
Compare
9540252
to
384d199
Compare
Log messages covered by tests should prefer `'%s'` over `%q` as these look better inside `""`.
…ng for debug content Currently the logger writes the debug level as `debug` but slog writees `DEBUG`. Making it ignore case, makes it work in both cases
384d199
to
e8ba4e5
Compare
e8ba4e5
to
f845e59
Compare
f845e59
to
3f70c4f
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why this PR?
What has changed?
Update some log messages to not use
%q
: as the default handler for slog places the value of each field, includingmessage
, inside""
, using%q
is not easy to read as it results inmessage="some \"thing\""
. Using''
, that is, writing'%s'
is better as it results inmessage="some 'thing'"
.In this PR, we only update what is necessary to get the existing tests to pass; a future PR will address the log messages in general.
Remove
internal/loggers
package, removego.uber.org/zap
andgithub.com/go-logr/zapr
dependencies.How does it do it?
How is it tested?
How does it affect users?